Point of presence management in request routing

ABSTRACT

A system and method for the management of client computing device DNS queries and subsequent resource requests within a content delivery network service provider domain are provided. The management of the DNS queries can include the selection of computing devices corresponding to various Point of Presence locations for processing DNS queries. Additionally, the management of the content requests can include the selection of computing devices corresponding to resource cache components corresponding to various Point of Presence locations for providing requested content. The selection of the computing devices can incorporate logic related to geographic criteria, testing criteria, and the like.

BACKGROUND

Generally described, computing devices and communication networks can beutilized to exchange information. In a common application, a computingdevice can request content from another computing device via acommunication network. For example, a user at a personal computingdevice can utilize a software browser application to request a Web pagefrom a server computing device via the Internet. In such embodiments,the user computing device can be referred to as a client computingdevice and the server computing device can be referred to as a contentprovider.

Content providers are generally motivated to provide requested contentto client computing devices, often with consideration of efficienttransmission of the requested content to the client computing deviceand/or consideration of a cost associated with the transmission of thecontent. For larger scale implementations, a content provider mayreceive content requests from a high volume of client computing devices,which can place a strain on the content provider's computing resources.Additionally, the content requested by the client computing devices mayhave a number of components, which can further place additional strainon the content provider's computing resources.

With reference to an illustrative example, a requested Web page, ororiginal content, may be associated with a number of additionalresources, such as images or videos, that are to be displayed with theWeb page. In one specific embodiment, the additional resources of theWeb page are identified by a number of embedded resource identifiers,such as uniform resource locators (“URLs”). In turn, software on theclient computing devices typically processes embedded resourceidentifiers to generate requests for the content. Often, the resourceidentifiers associated with the embedded resources reference a computingdevice associated with the content provider such that the clientcomputing device would transmit the request(s) for the additionalresources to the referenced content provider computing device.Accordingly, in order to satisfy a content request, the content providerwould provide client computing devices data associated with the Web pageas well as the data associated with the embedded resources (e.g.,embedded resource identifiers).

Some content providers attempt to facilitate the delivery of requestedcontent, such as Web pages and/or resources identified in Web pages,through the utilization of a content delivery network (“CDN”) serviceprovider. A CDN service provider typically maintains a number ofcomputing devices in a communication network that can maintain contentfrom various content providers. In turn, content providers can instruct,or otherwise suggest to, client computing devices to request some, orall, of the content provider's content from the CDN service provider'scomputing devices.

As with content providers, CDN service providers are also generallymotivated to provide requested content to client computing devices,often with consideration of efficient transmission of the requestedcontent to the client computing device and/or consideration of a costassociated with the transmission of the content. Accordingly, CDNservice providers often consider factors such as latency of delivery ofrequested content in order to meet service level agreements or togenerally improve the quality of delivery service. The consideration ofsuch factors can be applied with regard to decisions by a CDN serviceprovider as to which of the several available computing devices is bestsuited to process client computing device requests for content.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisinvention will become more readily appreciated as the same become betterunderstood by reference to the following detailed description, whentaken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of a content delivery environmentincluding a number of client computing devices, a content provider, anda content delivery network service provider;

FIG. 2 is a block diagram of the content delivery environment of FIG. 1illustrating the registration of a content provider with a contentdelivery service provider;

FIG. 3 is a block diagram of the content delivery environment of FIG. 1illustrating the generation and processing of a content request from aclient computing device to a content provider;

FIG. 4 is a block diagram of the content delivery environment of FIG. 1illustrating the generation and processing of a DNS query correspondingto an embedded resource from a client computing device to a contentdelivery network service provider;

FIG. 5 is a block diagram of the content delivery environment of FIG. 1illustrating the forwarding of a DNS query to an alternative DNS servercomponent;

FIG. 6 is a block diagram of the content delivery environment of FIG. 1illustrating the generation and processing of a DNS query withalternative resource identifiers;

FIG. 7 is a block diagram of the content delivery environment of FIG. 1illustrating the generation and processing of embedded resource requestsfrom a client computing device to a content delivery network serviceprovider;

FIG. 8 is a flow diagram illustrative of a request routing routineimplemented by a content delivery network service provider utilizationof a series of alternative resource identifiers;

FIG. 9 is a flow diagram illustrative of a Point of Presence selectionsub-routine implemented by a content delivery network service provider;

FIG. 10 is a flow diagram illustrative of a Point of Presence selectionsub-routine implemented by a content delivery network service provider;and

FIGS. 11-13 are block diagrams illustrative of the approximation ofgeographic distance of various nodes of a communication network for usein the selection of a Point of Presence location.

DETAILED DESCRIPTION

Generally described, aspects of the present disclosure are directed torouting of DNS queries from client computing devices. The DNS queriescorrespond to content requests provided by a network resource, such ascontent delivery network (“CDN”) service providers. Specifically,aspects of the disclosure will be described with regard to themanagement of client computing device DNS queries and subsequentresource requests within a content delivery network service providerdomain. Illustratively, the management of the DNS queries can includethe selection of computing devices corresponding to various Point ofPresence (“POP”) locations for processing DNS queries. Additionally, themanagement of the content requests can include the selection ofcomputing devices corresponding to resource cache componentscorresponding to various POP locations for providing requested content.The selection of the computing devices can incorporate logic related togeographic criteria, performance threshold criteria, testing criteria,and the like. Although various aspects of the disclosure will bedescribed with regard to illustrative examples and embodiments, oneskilled in the art will appreciate that the disclosed embodiments andexamples should not be construed as limiting.

FIG. 1 is a block diagram illustrative of content delivery environment100 for the management and processing of content requests. Asillustrated in FIG. 1, the content delivery environment 100 includes anumber of client computing devices 102 (generally referred to asclients) for requesting content from a content provider, a CDN serviceprovider, or other service provider. In an illustrative embodiment, theclient computing devices 102 can correspond to a wide variety ofcomputing devices, including personal computing devices, laptopcomputing devices, hand-held computing devices, terminal computingdevices, mobile devices, wireless devices, various electronic devicesand appliances and the like. In an illustrative embodiment, the clientcomputing devices 102 include necessary hardware and software componentsfor establishing communications over a communication network 108, suchas a wide area network or local area network. For example, the clientcomputing devices 102 may be equipped with networking equipment andbrowser software applications that facilitate communications via theInternet or an intranet.

Although not illustrated in FIG. 1, each client computing device 102 canutilize some type of local DNS resolver component, such as a DNS Nameserver, that generates the DNS queries attributed to the clientcomputing device 102. In one embodiment, the local DNS resolvercomponent may be provided by an enterprise network to which the clientcomputing device 102 belongs. In another embodiment, the local DNSresolver component may be provided by an Internet Service Provider(“ISP”) that provides the communication network connection to the clientcomputing device 102. However, for purposes of the present disclosure,communications facilitated through a network component, such as a DNSresolver component, will be illustrated as transmitted directly from theclient computing devices 102.

The content delivery environment 100 can also include a content provider104 in communication with the one or more client computing devices 102via the communication network 108. The content provider 104 illustratedin FIG. 1 corresponds to a logical association of one or more computingdevices associated with a content provider. Specifically, the contentprovider 104 can include a web server component 110 corresponding to oneor more server computing devices for obtaining and processing requestsfor content (such as Web pages) from the client computing devices 102.The content provider 104 can further include an origin server component112 and associated storage component 114 corresponding to one or morecomputing devices for obtaining and processing requests for networkresources from the CDN service provider. One skilled in the relevant artwill appreciate that the content provider 104 can be associated withvarious additional computing resources, such as additional computingdevices for administration of content and resources, DNS name servers,and the like. For example, although not illustrated in FIG. 1, thecontent provider 104 can be associated with one or more DNS name servercomponents that would be authoritative to resolve client computingdevice DNS queries corresponding to a domain of the content provider.

With continued reference to FIG. 1, the content delivery environment 100can further include a CDN service provider 106 in communication with theone or more client computing devices 102 and the content provider 104via the communication network 108. The CDN service provider 106illustrated in FIG. 1 corresponds to a logical association of one ormore computing devices associated with a CDN service provider.Specifically, the CDN service provider 106 can include a number of POPlocations 116, 122, 128 that correspond to nodes on the communicationnetwork 108. Each POP 116, 122, 128 includes a DNS component 118, 124,130 made up of a number of DNS server computing devices for resolvingDNS queries from the client computing devices 102. Each POP 116, 122,128 also includes a resource cache component 120, 126, 132 made up of anumber of cache server computing devices for storing resources fromcontent providers and transmitting various requested resources tovarious client computers. The DNS components 118, 124 and 130 and theresource cache components 120, 126, 132 may further include additionalsoftware and/or hardware components that facilitate communicationsincluding, but not limited to, load balancing or load sharingsoftware/hardware components.

In an illustrative embodiment, the DNS component 118, 124, 130 andresource cache component 120, 126, 132 are considered to be logicallygrouped, regardless of whether the components, or portions of thecomponents, are physically separate. Additionally, although the POPs116, 122, 128 are illustrated in FIG. 1 as logically associated with theCDN service provider 106, the POPs will be geographically distributedthroughout the communication network 108 in a manner to best servevarious demographics of client computing devices 102. Additionally, oneskilled in the relevant art will appreciate that the CDN serviceprovider 106 can be associated with various additional computingresources, such as additional computing devices for administration ofcontent and resources, and the like.

With reference now to FIGS. 2-7, the interaction between variouscomponents of the content delivery environment 100 of FIG. 1 will beillustrated. For purposes of the example, however, the illustration hasbeen simplified such that many of the components utilized to facilitatecommunications are not shown. One skilled in the relevant art willappreciate that such components can be utilized and that additionalinteractions would accordingly occur without departing from the spiritand scope of the present disclosure.

With reference to FIG. 2, an illustrative interaction for registrationof a content provider 104 with the CDN service provider 106 will bedescribed. As illustrated in FIG. 2, the CDN content registrationprocess begins with registration of the content provider 104 with theCDN service provider 106. In an illustrative embodiment, the contentprovider 104 utilizes a registration application program interface(“API”) to register with the CDN service provider 106 such that the CDNservice provider 106 can provide content on behalf of the contentprovider 104. The registration API includes the identification of theorigin server 112 of the content provider 104 that will providerequested resources to the CDN service provider 106.

One skilled in the relevant art will appreciate that upon identificationof appropriate origin servers 112, the content provider 104 can begin todirect requests for content from client computing devices 102 to the CDNservice provider 106. Specifically, in accordance with DNS routingprinciples, a client computing device request corresponding to aresource identifier would eventually be directed toward a POP 116, 122,128 associated with the CDN service provider 106. In the event that theresource cache component 120, 126, 132 of a selected POP does not have acopy of a resource requested by a client computing device 102, theresource cache component will request the resource from the originserver 112 previously registered by the content provider 104.

With continued reference to FIG. 2, upon receiving the registration API,the CDN service provider 106 obtains and processes the registrationinformation. In an illustrative embodiment, the CDN service provider 106can then generate additional information that will be used by the clientcomputing devices 102 as part of the content requests. The additionalinformation can include, without limitation, client identifiers, such asclient identification codes, content provider identifiers, such ascontent provider identification codes, executable code for processingresource identifiers, such as script-based instructions, and the like.One skilled in the relevant art will appreciate that various types ofadditional information may be generated by the CDN service provider 106and that the additional information may be embodied in any one of avariety of formats.

Illustratively, the CDN service provider 106 returns an identificationof applicable domains for the CDN service provider (unless it has beenpreviously provided) and any additional information to the contentprovider 104. In turn, the content provider 104 can then process thestored content with content provider specific information. In oneexample, as illustrated in FIG. 2, the content provider 104 translatesresource identifiers originally directed toward a domain of the originserver 112 to a domain corresponding to the CDN service provider. Thetranslated URLs are embedded into requested content in a manner suchthat DNS queries for the translated URLs will resolve to a DNS severserver corresponding to the CDN service provider 106 and not a DNSserver corresponding to the content provider 104. Although thetranslation process is illustrated in FIG. 2, in some embodiments, thetranslation process may be omitted in a manner described in greaterdetail below.

Generally, the identification of the resources originally directed tothe content provider 104 will be in the form of a resource identifierthat can be processed by the client computing device 102, such asthrough a browser software application. In an illustrative embodiment,the resource identifiers can be in the form of a uniform resourcelocator (“URL”). Because the resource identifiers are included in therequested content directed to the content provider, the resourceidentifiers can be referred to generally as the “content provider URL.”For purposes of an illustrative example, the content provider URL canidentify a domain of the content provider 104 (e.g.,contentprovider.com), a name of the resource to be requested (e.g.,“resource.xxx”) and a path where the resource will be found (e.g.,“path”). In this illustrative example, the content provider URL has theform of:

http://www.contentprovider.com/path/resource.xxx

During an illustrative translation process, the content provider URL ismodified such that requests for the resources associated with thetranslated URLs resolve to a POP associated with the CDN serviceprovider 106. In one embodiment, the translated URL identifies thedomain of the CDN service provider 106 (e.g., “cdnprovider.com”), thesame name of the resource to be requested (e.g., “resource.xxx”) and thesame path where the resource will be found (e.g., “path”). Additionally,the translated URL can include additional processing information (e.g.,“additional information”). The translated URL would have the form of:

http://additional_information.cdnprovider.com/path/resources.xxx

In another embodiment, the information associated with the CDN serviceprovider 106 is included in the modified URL, such as through prependingor other techniques, such that the translated URL can maintain all ofthe information associated with the original URL. In this embodiment,the translated URL would have the form of:

http://additional_information.cdnprovider.com/www.contentprovider.com/path/resource.xxx

With reference now to FIG. 3, after completion of the registration andtranslation processes illustrated in FIG. 2, a client computing device102 subsequently generates a content request that is received andprocessed by the content provider 104, such as through the Web server110. In accordance with an illustrative embodiment, the request forcontent can be in accordance with common network protocols, such as thehypertext transfer protocol (“HTTP”). Upon receipt of the contentrequest, the content provider 104 identifies the appropriate responsivecontent. In an illustrative embodiment, the requested content cancorrespond to a Web page that is displayed on the client computingdevice 102 via the processing of information, such as hypertext markuplanguage (“HTML”), extensible markup language (“XML”), and the like. Therequested content can also include a number of embedded resourceidentifiers, described above, that correspond to resource objects thatshould be obtained by the client computing device 102 as part of theprocessing of the requested content. The embedded resource identifierscan be generally referred to as original resource identifiers ororiginal URLs regardless of whether they have been translated in themanner described above.

Upon receipt of the requested content, the client computing device 102,such as through a browser software application, begins processing any ofthe markup code included in the content and attempts to acquire theresources identified by the embedded resource identifiers. Accordingly,the first step in acquiring the content corresponds to the issuance, bythe client computing device 102 (through its local DNS resolver), a DNSquery for the original URL resource identifier that results in theidentification of a DNS server authoritative to the “.” and the “com”portions of the translated URL. After resolving the “.” and “com”portions of the embedded URL, the client computing device 102 thenissues a DNS query for the resource URL that results in theidentification of a DNS server authoritative to the “.cdnprovider”portion of the embedded URL. The issuance of DNS queries correspondingto the “.” and the “com” portions of a URL are well known and have notbeen illustrated.

With reference now to FIG. 4, in an illustrative embodiment, thesuccessful resolution of the “cdnprovider” portion or “contentprovider”portion of the original URL identifies a network address, such as an IPaddress, of a DNS server associated with the CDN service provider 106.In one embodiment, the IP address is a specific network address uniqueto a DNS server component of a POP. In another embodiment, the IPaddress can be shared by one or more POPs. In this embodiment, a furtherDNS query to the shared IP address utilizes a one-to-many networkrouting schema, such as anycast, such that a specific POP will receivethe request as a function of network topology. For example, in ananycast implementation, a DNS query issued by a client computing device102 to a shared IP address will arrive at a DNS server componentlogically having the shortest network topology distance, often referredto as network hops, from the client computing device. The networktopology distance does not necessarily correspond to geographicdistance. However, in some embodiments, the network topology distancecan be inferred to be the shortest network distance between a clientcomputing device 102 and a POP.

With continued reference to FIG. 4, in either of the above identifiedembodiments (or any other embodiment), a specific DNS server in the DNScomponent 118 of a POP 116 receives the DNS query transmitted by theclient computing device 102 and corresponding to the original URL of theembedded resource identifier. Once one of the DNS servers in the DNScomponent 118 receives the request, the specific DNS server attempts toresolve the request. Generally, a specific DNS server can resolve theDNS query by identifying an IP address of a cache server component thatwill process the request for the requested resource. As described above,a selected resource cache component can process the request by eitherproviding the requested resource if it is available or attempting toobtain the requested resource from another source, such as a peer cacheserver computing device or the origin server 112 of the content provider104.

In one embodiment, the DNS server resolves the DNS query by providingthe IP address of a default resource cache component associated with thereceiving DNS server, such as the resource cache component located atthe same POP. In this embodiment, the CDN service provider 106illustratively has utilized logic in the selection of the receiving DNSserver component. In another embodiment, the receiving DNS servercomponent can utilize additional or alternative logic in selectingresource cache components associated with various POPs provided by theCDN service provider 106. In this embodiment, the example routines forthe selection of alternative DNS servers illustrated in FIGS. 8-10 couldbe applied in the selection of a resource cache component.

Referring now to FIGS. 5 and 6, if the receiving DNS server is notcapable of resolving the DNS query (e.g., the receiving DNS server isnot authoritative) or if CDN service provider 106 determines thatanother DNS server at another POP should resolve the DNS server, thespecific receiving DNS server will cause the DNS query to be received byanother DNS server. Example routines for the selection of alternativeDNS query will be described with regard to FIGS. 8-10. As will beexplained in greater detail below, the routing of a received DNS queryto an alternative DNS server component can be achieved in variousmanners and can be implemented independently of any additional logic inthe identification of one or more resource cache components (e.g.,resolution of the DNS query) or in conjunction with additional oralternative logic utilized in the identification of one or more resourcecache components.

With reference to FIG. 5, in one alternative embodiment for causing thereceipt of a DNS query by another DNS server, the receiving DNS servercan process additional information included in an original URL DNS queryand utilize logic to select an alternative DNS server provided by theCDN service provider 106 or another service provider. With reference tothe previous illustrative original URL format, the receiving DNS servercan parse the “additional information” included in the URL correspondingto the DNS query and apply various request routing criteria to identifyone or more DNS server best suited to attempt to resolve the DNS query.For example, the additional information included in the URL can identifyservice plan information, geographic identifiers, account identifiers orother information utilized by the receiving DNS server to select anappropriate alternative DNS server. Example routines for the selectionof alternative DNS servers will be discussed in greater detail below. Asillustrated in FIG. 5, the receiving DNS server, such as a specific DNSserver in the DNS component 118 of a POP 116, would forward the receivedDNS query to the DNS component 124 of POP 122. In this embodiment, theforwarding of the DNS query to an alternative POP may be achievedwithout additional interaction between the receiving DNS component 118and the requesting client computing device.

With reference now to FIG. 6, in another alternative embodiment forcausing the receipt of a DNS query by another DNS server, the CDNservice provider 106 can maintain sets of various alternative resourceidentifiers that cause the client computing device 102 to transmit oneor more subsequent DNS queries. The alternative resource identifiers canbe provided by the CDN service provider 106 to the client computingdevice 102 such that a subsequent DNS query on the alternative resourceidentifier will resolve to a different DNS server component within theCDN service provider's network. In an illustrative embodiment, thealternative resource identifiers are in the form of one or morecanonical name (“CNAME”) records. In one embodiment, each CNAME recordidentifies a domain of the CDN service provider 106 (e.g.,“cdnprovider.com” or “cdnprovider-1.com”). As will be explained ingreater detail below, the domain in the CNAME does not need to be thesame domain found in original URL or in a previous CNAME record.Additionally, each CNAME record includes additional information, such asrequest routing information, (e.g., “request routing information”). Anillustrative CNAME record can have the form of:

CNAME request_routing_information.cdnprovider.com

In accordance with an illustrative embodiment utilizing CNAMES, the DNSserver maintains a data store that defines CNAME records for variousoriginal URLs. If a DNS query corresponding to a particular original URLmatches an entry in the data store, the DNS server component 118 returnsa CNAME record as defined in the data store. In an illustrativeembodiment, the data store can include multiple CNAME recordscorresponding to a particular original URL. The multiple CNAME recordswould define a set of potential candidates that can be returned to theclient computing device. In such an embodiment, the DNS server component118, either directly or via a network-based service, can implementadditional logic in selecting an appropriate CNAME from a set ofpossible of CNAMEs. In an illustrative embodiment, each DNS servercomponent 118, 124, 130 maintains the same data stores that define CNAMErecords, which can be managed centrally by the CDN service provider 106.Alternatively, each DNS server component 118, 124, 130 can have a POPspecific data stores that define CNAME records, which can be managedcentrally by the CDN service provider 106 or locally at the POP 116,122, 128.

The returned CNAME can also include request routing information that isdifferent from or in addition to the information provided in URL/CNAMEof the current DNS query. For example, if the CNAME selection is basedon regional plan, a specific regional plan can be identified in the“request_routing_information” portion of the specific CNAME record. Asimilar approach could be taken to identify service level plans and filemanagement by including a specific identifier in the“request_routing_information” portion of the CNAME record. In anotherembodiment, request routing information can be found in theidentification of a CDN service provider 106 domain different from thedomain found in the current URL/CNAME. For example, if the CNAME isbased on regional plan, a specific regional plan domain (e.g.,“cdnprovder-region1.com”) could be used in the domain name portion ofthe specific CNAME record. Any additional request routing informationcan be prepended to the existing request routing information in thecurrent URL/CNAME such that the previous request routing informationwould not be lost (e.g., CNAMEserviceplan.regionalplan.cdnprovider.com). One skilled in the relevantart will appreciate that additional or alternative techniques and/orcombination of techniques may be used to include the additional requestrouting information in the CNAME record that is selected by the DNSserver component 118.

One skilled in the relevant art will appreciate that DNS servercomponent 118 may select (or otherwise obtain) a CNAME record that isintended resolve to a more appropriate DNS server of the CDN serviceprovider 106. It may be possible, however, that the same DNS serverwould also be authoritative for the subsequent DNS query for the CNAMEto be provided to the client computing device. In such an embodiment,the DNS server, such as DNS server component 118, may choose to resolvethe future DNS query in advance.

With continued reference to FIG. 6, upon receipt of the CNAME from theDNS server component 118, the client computing device 102 generates asubsequent DNS query corresponding to the CNAME. As previously discussedwith regard to FIG. 4, the DNS query process could first start with DNSqueries for the “.” and “com” portions, followed by a query for the“cdnprovider” portion of the CNAME. To the extent, however, that theresults of a previous DNS queries can be cached (and remain valid), theclient computing device 102 can utilize the cached information and doesnot need to repeat the entire process. However, at some point, dependingon whether the CNAME provided by DNS server component 118 and theprevious URL/CNAME share common CDN service provider domains, the DNSquery resolves to a different POP provided by the CDN service provider106. As illustrated in FIG. 6, the DNS server component 124 of POP 122is now authoritative based on the different information in the currentCNAME previously provided by the DNS server component 118. As previouslydescribed, the DNS server component 124 can then determine whether toresolve the DNS query on the CNAME with an IP address of a cachecomponent that will process the content request or whether to provideanother alternative resource identifier selected in the manner describedabove.

In an illustrative embodiment, the receiving DNS server components, suchas DNS server component 130, can utilize a variety of information inselecting a resource cache component. In one example, the DNS servercomponent can default to a selection of a resource cache component ofthe same POP. In another example, the DNS server components can select aresource cache component based on various load balancing or load sharingalgorithms. Still further, the DNS server components can utilize networkperformance metrics or measurements to assign specific resource cachecomponents. The IP address selected by a DNS server component maycorrespond to a specific caching server in the resource cache.Alternatively, the IP address can correspond to a hardware/softwareselection component (such as a load balancer).

With reference now to FIG. 7, in an illustrative example, assuming inthe various embodiments described with regard to FIGS. 4, 5 and 6 that areceiving DNS server component has resolved a DNS query and identifiedthe IP address of a resource cache component for providing the requestedresource, upon receipt of the IP address for the resource cachecomponent 132, the client computing device 102 transmits requests forthe requested content to the resource cache component 132. The resourcecache component 132 processes the request in a manner described aboveand the requested content is transmitted to the client computing device102.

With reference now to FIG. 8, a request routine 800 implemented by theCDN service provider 106 will be described. One skilled in the relevantart will appreciate that actions/steps outlined for routine 800 may beimplemented by one or many computing devices/components that areassociated with the CDN service provider 106. Accordingly, routine 800has been logically associated as being performed by the CDN serviceprovider 106.

At block 802, one of the DNS server components 118, 124, 130 receives aDNS query corresponding to resource identifier. As previously discussed,the resource identifier can be a URL that has been embedded in contentrequested by the client computing device 102 and previously provided bythe content provider 104. Alternatively, the resource identifier canalso correspond to a CNAME provided by a content provider DNS server inresponse to a DNS query previously received from the client computingdevice 102. At decision block 804, a test is conducted to determinewhether the current DNS server is authoritative to resolve the DNSquery. In an illustrative embodiment, the DNS server can determinewhether it is authoritative to resolve the DNS query if there are noCNAME records corresponding to the received resource identifier. Inanother embodiment, the DNS server can parse any additional informationincluded in the URL corresponding to the DNS query and utilize theadditional information to determine whether the receiving DNS servercomponent is authoritative. For example, the additional information inthe URL may include information, such as an identifier, that identifiesthe authoritative DNS server. Alternative or additional methodologiesmay also be practiced to determine whether the DNS server isauthoritative.

If at decision block 804 the DNS server is not authoritative, at block806, the DNS server component selects an alternative DNS server. Asdescribed above, in one embodiment, the receiving DNS server can selectan alternative DNS server by utilizing an alternative resourceidentifier, such as a CNAME. In this embodiment, the receiving DNSserver component can utilize a data store to identify an appropriateCNAME as a function of the current DNS query. Additionally, the DNSserver component can also implement additional logical processing toselect from a set of potential CNAMEs. In another embodiment, thereceiving DNS server can forward the DNS query via the communicationnetwork to another DNS sever server component. Two example sub-routinesfor selection of the alternative DNS server will be described withregard to FIGS. 9 and 10. The routine 800 returns to block 802 whereanother DNS server component of the CDN service provider 106 receivesthe forwarded DNS query or a subsequent DNS query corresponding to areturned CNAME.

With reference again to block 804, if the receiving DNS server isauthoritative (including a determination that the same DNS server willbe authoritative for subsequent DNS queries), then at decision block808, the receiving DNS server component determines whether anyalternative DNS server should be selected.

In one embodiment, a receiving DNS server component may be authoritativebecause it can resolve the DNS query. However, the CDN service provider106 may wish to have another authoritative server resolve the request.For example, the CDN service provider 106 may wish to balance therequest requests among several DNS servers. In another example, the CDNservice provider 106 may wish to test the performance of the DNS servercomponent associated with other POPs in the CDN service providersdomain. If the DNS server component is determined to select analternative server, at block 810, the receiving DNS server selects analternative DNS servers. As described above, in one embodiment, thereceiving DNS server can select an alternative DNS server by utilizingan alternative resource identifier, such as a CNAME. In this embodiment,the receiving DNS server component can utilize a data store to identifyan appropriate CNAME as a function of the current DNS query.Additionally, the DNS server component can also implement additionallogical processing to select from a set of potential CNAMEs. In anotherembodiment, the receiving DNS server can forward the DNS query via thecommunication network to another DNS server component. Two examplesub-routines for selection of the alternative DNS server will bedescribed with regard to FIGS. 9 and 10. The routine 800 returns toblock 802 where another DNS server component of the CDN service provider106 receives the forwarded DNS query or a subsequent DNS querycorresponding to a returned CNAME.

Referring again to decision block 808, if the receiving DNS server doesnot select an alternative server, the current DNS server resolves theDNS query by returning the IP address of cache server component. In anon-limiting manner, a number of methodologies for selecting anappropriate resource cache component have been previously discussed. Forexample, the receiving DNS server can implement the logic described inselecting the alternative DNS servers in FIGS. 9 and 10 to select aresource cache component. In another example, the receiving DNS servercan select a default resource cache component, such as the resourcecache component associated with the POP of the receiving DNS server.Additionally, as described above, the IP address may correspond to aspecific cache server of a resource cache component or generally to agroup of cache servers.

Referring now to FIG. 9, a flow diagram illustrative of a Point ofPresence selection sub-routine 900 based on a minimum performancethreshold and implemented by the CDN service provider 106 will bedescribed. One skilled in the relevant art will appreciate thatactions/steps outlined for sub-routine 900 may be implemented by one ormany computing devices/components that are associated with the CDNservice provider 106. Accordingly, sub-routine 900 has been logicallyassociated as being performed by the CDN service provider 106.Additionally, as described above, although sub-routine 900 will bedescribed with regard to the selection of alternative DNS servercomponents, sub-routine 900 may be implemented by a DNS server in theselection of resource cache components in resolving a DNS query.

At block 902, the DNS server obtains performance measurement informationfor a set of target POPs in the CDN service provider domain. In anillustrative embodiment, the set of target POPs can correspond to allthe POPs within a CDN service provider 106 domain or a subset of POPsidentified by other criteria, such as service level plans, geographiclimitations, and the like. Illustratively, the performance measurementinformation corresponds to at least one value or category related to thedelivery of resources. In one embodiment, the performance measurementinformation can correspond to values related to latency measurementinformation for providing resources. The latency information can beassociated with the requesting client computing device 102, such aslatency information from previous interactions with the specific clientcomputing device. The latency information can also be associated withgroupings of client computing devices 102, such as by ISP, geographiclocation, enterprise networks, DNS resolver components, and the like.Additionally, the latency information may be determined based onabsolute latency measurements or relative latency measurements.

In another embodiment, the performance measurement information cancorrespond to categories, or levels, of performance as determined by theCDN service provider 106, ISPs, client computing devices 102 or otherentity. For example, the performance measurement information cancorrespond to a classification of a POP according to a category (e.g.,“gold” or “silver”) based on historical information. The categoryinformation may be measured in terms of absolute performance or relativeperformance according to other POPs. Still further, the categoryinformation may also be organized in accordance with other criteria,such as geographic organizational criteria, network affiliationorganizational criteria, organization affiliation organizationalcriteria, and the like. One skilled in the relevant art will appreciatethat additional or alternative performance measurement information mayalso be utilized or combined.

At block 904, the DNS server obtains minimum performance thresholds forselecting a POP. The performance threshold or set of performancethresholds will correspond to the performance information obtained inblock 902. The performance threshold information may be maintainedcentrally by the CDN service provider 106 or managed individually ateach POP (or by a set of POPs). At block 906, the sub-routine 900proceeds to a loop by selecting the next POP in the set of POPsavailable to process the DNS query. At decision block 908, a test isconducted to determine whether the performance information associatedwith the currently selected POP is above the performance threshold. Ifso, the POP is added to a set of POPs available for selection at block910.

If at decision block 908, the performance measurement information is notabove the performance threshold, or once a POP has been added to the setof POPs available for selection, at decision block 912, a test isconducted to determine whether there are additional POPs in the originalset of POPs. If so, the sub-routine 900 returns to block 906 forprocessing of the performance measurement information for the next POPin the original set of POPs. Alternatively, if no additional POPs remainin the original set of POPs, the sub-routine 900 returns with theselection of POP from the set of available POPs. In one embodiment, thePOP selection can be based on a relative comparison of performancemeasurement information (e.g., the POP associated with the lowestlatency). In another embodiment, the POP selection can be based onrandom selection or a weighted selection based on performancemeasurement information. In still another embodiment, additionalcriteria, such as geographic criteria, cost criteria, etc. may beutilized to select a POP from the set of available POPs.

Referring now to FIG. 10, a flow diagram illustrative of a Point ofPresence selection sub-routine 1000 based on approximated geographicdistance and implemented by the CDN service provider 106 will bedescribed. One skilled in the relevant art will appreciate thatactions/steps outlined for sub-routine 1000 may be implemented by one ormany computing devices/components that are associated with the CDNservice provider 106. Accordingly, sub-routine 1000 has been logicallyassociated as being performed by the CDN service provider 106.Additionally, as described above, although sub-routine 1000 will bedescribed with regard to the selection of alternative DNS servercomponents, sub-routine 1000 may be implemented by a DNS server in theselection of resource cache components in resolving a DNS query.

At block 1002, the DNS server obtains performance measurementinformation for a set of target POPs in the CDN service provider domain.In an illustrative embodiment, the set of target POPs can correspond toall the POPs within a CDN service provider 106 domain or a subset ofPOPs identified by other criteria, such as service level plans,geographic limitations, and the like. In one embodiment, the performancemeasurement information can correspond to values related to latencymeasurement information for providing resources. The latency informationcan be associated with the requesting client computing device 102, suchas latency information from previous interactions with the specificclient computing device. The latency information can also be associatedwith groupings of client computing devices 102, such as by ISP,geographic location, enterprise networks, DNS resolver components, andthe like. One skilled in the relevant art will appreciate thatadditional or alternative performance measurement information may alsobe utilized or combined.

At block 1004, the sub-routine 1000 proceeds to a loop by selecting thenext POP in the set of POPs available to process the DNS query. At block1006, the DNS server determines a maximum distance between therequesting client computing device (or other starting position) and thePOP. In an illustrative embodiment, the maximum distance between areference node and the POP corresponds to the product of the latencyinformation for the reference node and the maximum speed for packetdelivery. Illustratively, the reference node can correspond to a varietyof network nodes or other identifiable components including, but notlimited to, the client computing device 102, DNS servers, DNS resolvers,network storage location, network computing device locations, mobileterminals, mobile infrastructure equipment, and the like.

With reference to FIG. 11, assume that a portion of the communicationnetwork 108 includes a number of nodes 1102-1128. Assume that the clientcomputing device 102 corresponds to node 1102 and that CDN serviceprovider's domain includes POPs corresponding to nodes 1116, 1118 and1124. As also illustrated in FIG. 11, the actual path of communicationsbetween node 1102 and 1116, path 1130, corresponds to networkintermediate communications through nodes 1110, 1112 and 1114. Likewise,the actual path of communications between node 1102 and 1118, path 1134,corresponds to network intermediate communications through node 1110.Still further, the actual path of communications between node 1102 and1124, path 1134, corresponds to network intermediate communicationsthrough nodes 1108, 1120, and 1122. With reference now to FIG. 12, itcan be assumed that the maximum distance between node 1102 and nodes1116, 1118 and 1124, respectively paths 1130, 1132 and 1134 is astraight line between the two nodes the distance of which is the productof the latency in communications and the maximum speed of communications(e.g., the speed of light). In this embodiment, the latency caused bythe intermediate nodes in the actual network paths is ignored forpurposes of determining the maximum geographic distance between thestarting nodes and the POPs.

At decision block 1008, a test is conducted to determine whether themaximum distance associated with the currently selected POP is above themaximum geographic threshold allowed for a POP. If not, the POP is addedto a set of POPs available for selection at block 1010. FIG. 13illustrates the three calculated maximum distances for paths 1130, 1132,1134 between node 1102 and nodes 1116, 1118, and 1124, respectively.Additionally, the maximum geographic threshold is illustrated as acircle 1136 having a radius corresponding to the calculated maximumgeographic threshold from the central node in any direction. Asillustrated in FIG. 13, the calculated maximum geographic distance forpath 1130 and 1132 is within the maximum geographic threshold 1136,while the calculated maximum geographic distance for path 1134 is abovethe maximum geographic threshold 1136. One skilled in the relevant artwill appreciate that alternative geographic shapes or multiplegeographic maximums may be implemented.

If at decision block 1008, the calculated geographic distance is abovethe maximum distance, or once a POP has been added to the set of POPsavailable for selection, at decision block 1012, a test is conducted todetermine whether there are additional POPs in the original set of POPs.If so, the sub-routine 1000 returns to block 1004 for processing of theperformance measurement information for the next POP in the original setof POPs. Alternatively, if no additional POPs remain in the original setof POPs, the sub-routine 1000 returns with the selection of POP from theset of available POPs. In one embodiment, the POP selection can be basedon a relative comparison of performance measurement information (e.g.,the POP associated with the lowest latency). In another embodiment, thePOP selection can be based on random selection or a weighted selectionbased on performance measurement information. In still anotherembodiment, additional criteria, such as geographic criteria, costcriteria, etc. may be utilized to select a POP from the set of availablePOPs.

While illustrative embodiments have been disclosed and discussed, oneskilled in the relevant art will appreciate that additional oralternative embodiments may be implemented within the spirit and scopeof the present invention. Additionally, although many embodiments havebeen indicated as illustrative, one skilled in the relevant art willappreciate that the illustrative embodiments do not need to be combinedor implemented together. As such, some illustrative embodiments do notneed to be utilized or implemented in accordance with scope ofvariations to the present disclosure.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art. It willfurther be appreciated that the data and/or components described abovemay be stored on a computer-readable medium and loaded into memory ofthe computing device using a drive mechanism associated with acomputer-readable medium storing the computer executable components,such as a CD-ROM, DVD-ROM, or network interface; further, the componentand/or data can be included in a single device or distributed in anymanner. Accordingly, general purpose computing devices may be configuredto implement the processes, algorithms and methodology of the presentdisclosure with the processing and/or execution of the various dataand/or components described above.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure and protected by the following claims.

What is claimed is:
 1. A computer-implemented method for processingcontent requests comprising: obtaining, by a content delivery network(CDN) service provider, at a first DNS server a DNS query from a clientcomputing device, wherein the DNS query corresponds to a requestedresource, wherein the DNS query is associated with an original resourceidentifier which corresponds to a uniform resource locator such that theDNS query resolves to a domain corresponding to the CDN serviceprovider; dynamically identifying two or more alternative DNS serversoperative to receive DNS queries; determining a calculated maximumdistance for individual ones of the two or more alternative DNS servers,the calculated maximum distance determined as a product of a latencytime between respective individual ones of the two or more alternativeDNS servers and a reference node in the communication network; selectingan alternative DNS server from the identified two or more alternativeDNS servers, the alternative DNS server being selected as a function ofat least a comparison between a threshold maximum distance and thecalculated maximum distance associated with individual ones of the twoor more alternative DNS servers; transmitting an alternative resourceidentifier corresponding to the selected alternative DNS server to theclient computing device; obtaining a subsequent DNS query from theclient computing device at the selected alternative DNS server, whereinthe subsequent DNS query corresponds to the alternative resourceidentifier provided by the CDN service provider; determining whether theselected alternative DNS server is authoritative to the subsequent DNSquery; selecting a cache component for providing content associated withthe original resource identifier if the selected alternative DNS serveris authoritative to the subsequent DNS query; and transmittinginformation identifying the selected cache component if the selectedalternative DNS server is determined to be authoritative.
 2. The methodas recited in claim 1, wherein the selected alternative DNS servercorresponds to the CDN service provider.
 3. The method as recited inclaim 1, wherein the original resource identifier is provided by acontent provider and wherein the content provider is different from theCDN service provider.
 4. The method as recited in claim 1, wherein thealternative resource identifier corresponds to a canonical name recordidentifier.
 5. The method as recited in claim 1, wherein the originalresource identifier and the alternative resource identifier includeinformation identifying a same domain corresponding to the CDN serviceprovider.
 6. The method as recited in claim 1, wherein the originalresource identifier includes information identifying a first domaincorresponding to the CDN service provider and wherein the alternativeresource identifier includes information identifying a second domaincorresponding to the CDN service provider.
 7. The method as recited inclaim 1, wherein the original resource identifier is provided by atleast one of a content provider or a CDN service provider, the CDNservice provider different from the content provider.
 8. The method asrecited in claim 1, wherein the reference node corresponds to the clientcomputing device.
 9. The method as recited in claim 1, wherein thereference node corresponds to a communication network node.
 10. Themethod as recited in claim 9, wherein the reference node corresponds toat least one of mobile network infrastructure equipment, a DNS server, aDNS resolver component, or a router.
 11. A system for request routingcomprising: a first network point of presence associated with a contentdelivery network (CDN) service provider, wherein the first network pointof presence includes a DNS server that receives a DNS query from aclient computing device, wherein the DNS query corresponds to requestedcontent associated with an original resource identifier, and wherein theDNS server in the first network point of presence includes a hardwarecomponent and is operative to: identify two or more alternative DNSservers operative to receive DNS queries; determine a calculated maximumdistance for individual ones of the two or more alternative DNS servers,the calculated maximum distance determined as a product of a latencytime and a speed of transmission, the latency time being betweenrespective individual ones of the two or more alternative DNS serversand a reference node; select an alternative DNS server from theidentified two or more alternative DNS servers, the alternative DNSserver being selected as a function of at least a comparison between athreshold maximum distance and the calculated maximum distanceassociated with individual ones of the two or more alternative DNSservers; and transmit an alternative resource identifier correspondingto the selected alternative DNS server to the client computing device;and a second network point of presence, wherein the second network pointof presence includes the selected alternative DNS server and wherein theselected alternative DNS server includes a hardware component and isoperative to: obtain a subsequent DNS query from the client computingdevice, wherein the subsequent DNS query corresponds to the alternativeresource identifier provided by the CDN service provider; determinewhether the selected alternative DNS server is authoritative to thesubsequent DNS query; select a cache component for providing contentassociated with the original resource identifier if the selectedalternative DNS server is authoritative to the subsequent DNS query; andtransmit information identifying the selected cache component if theselected alternative DNS server is determined to be authoritative. 12.The system as recited in claim 11, wherein the second network point ofpresence is associated with the CDN service provider.
 13. The system asrecited in claim 11, wherein the original resource identifier isprovided by a content provider and wherein the content provider isdifferent from the CDN service provider.
 14. The system as recited inclaim 11, wherein the alternative resource identifier corresponds to acanonical name record identifier.
 15. The system as recited in claim 11,wherein information identifying the identified cache component to theclient computing device includes a network address of a cache componentin the second network point of presence.
 16. The system as recited inclaim 11, wherein information identifying the identified cache componentto the client computing device includes a network address of a cachecomponent in another network point of presence.
 17. The system asrecited in claim 11, wherein the original resource identifier and thealternative resource identifier include information identifying a samedomain corresponding to the CDN service provider.
 18. The system asrecited in claim 11, wherein the original resource identifier includesinformation identifying a first domain corresponding to the CDN serviceprovider and wherein the alternative resource identifier includesinformation identifying a second domain corresponding to the CDN serviceprovider.
 19. The system as recited in claim 11, wherein the originalresource identifier is provided by at least one of a content provider ora CDN service provider, the CDN service provider different from thecontent provider.
 20. The system as recited in claim 11, wherein thereference node corresponds to the client computing device.
 21. Thesystem as recited in claim 11, wherein the reference node corresponds toa communication network node.
 22. The system as recited in claim 21,wherein the reference node corresponds to at least one of mobile networkinfrastructure equipment, a DNS server, a DNS resolver component, or arouter.